It will make it visible in the logcat, for instance in Android Studio.
As a general rule, we should use babl_log() for anything which we
consider as "logs", unless we want to direct them to a given output for
sure (for instance in the case of CLI tools where we want the output to
be on standard I/O in terminal, fprintf() still is the best choice).
babl_free (path);
if (babl_db_count (db) <= 1)
{
- fprintf (stderr,
-"WARNING: the babl installation seems broken, no extensions found in queried\n"
-"BABL_PATH (%s) this means no SIMD/instructions/special case fast paths and\n"
-"only slow reference conversions are available, applications might still\n"
-"run but software relying on babl for conversions will be slow\n", dir_list);
+ babl_log ("WARNING: the babl installation seems broken, no extensions found in queried\n"
+ "BABL_PATH (%s) this means no SIMD/instructions/special case fast paths and\n"
+ "only slow reference conversions are available, applications might still\n"
+ "run but software relying on babl for conversions will be slow\n", dir_list);
}
}